Add TrustStore Support for Fetching OpenAPI via HTTPS with Self-Signed Certificates #136
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This Pull Request introduces enhancements to the plugin to support using a custom
TrustStore
. This feature is crucial for fetching OpenAPI documentation over HTTPS in environments that utilize self-signed certificates, especially in local development setups.Changes Made
TrustStore Configuration: Added properties
trustStore
andtrustStorePassword
to allow specifying a customTrustStore
.SSL Context Adjustment: Modified the SSL context setup within the plugin to include the
TrustStore
, ensuring self-signed certificates are trusted during SSL handshakes. WhenTrustStore
is not provided default SSL context is used.Motivation
In our current setup, fetching OpenAPI documentation over HTTPS fails due to untrusted self-signed certificates. By enabling
TrustStore
configuration, developers can easily add their self-signed certificates to theTrustStore
, circumventing the SSL handshake issue.Testing
TrustStore
.Usage
Set the new properties in the application's configuration to point to the custom
TrustStore
and its password:Request for Review
I kindly request a thorough review of these changes, focusing particularly on the SSL context modifications and the implementation of the new properties. Any feedback or suggestions to further optimize this feature are welcome.
fixes #135